So python-yaml is now a required dependency for sverchok? Can we work without it?

No need for dependencies. I made primitive parser for the file.

@vicdoval @Moult @mostaphaRoudsari @wassimj

After the PR the API of adding new categories to Sverchok's Add Node menu will be changed. Also it can lead to some problems in imports. It will be possible to add new categories in this way:

import sverchok.ui.nodeview_space_menu as sm
sm.add_node_menu.append_from_config(config)

def register():
    sm.add_node_menu.register()

The format of config structure -

[option, option, ..., menu item, menu item, ...]

Menu item can be one of next elements:

• '---' - String of a dotted line to define separator.
• 'SomeNode' - String of node bl_idname to define Add Node operator.
• {'Sub category name': [option, menu_item, ...]} - Dictionary of
  a subcategory.
• {'Operator name': [option, ...]} - Dictionary of a custom opeartor
  to call. Options for operator call are not supported currently.
• {'Menu name': [option, ...]} - Custom menu to show.

Options have such format - {'option_name': value}. They can be added
to sub categories, operators and custom menus.

Categories can have next options:

• {'icon_name': 'SOME_ICON'} - Value can be a string of standard Blender
  icons or Sverchok icon.

• {'extra_menu': 'menu_name'} - Values is a name of one of extra menus.
  Possible values:

  • "BasicDataPartialMenu"
  • "MeshPartialMenu"
  • "AdvancedObjectsPartialMenu"
  • "ConnectionPartialMenu"
  • "UiToolsPartialMenu"

Operators options:

• {"icon_name": "SOME_ICON"} - Icon to show in the menu.
• {"operator": "operator id name"} - bl_idname of operator to call.

Custom menus options:

• {"icon_name": "SOME_CION"} - Icon to show in menu.
• {"custom_menu": "menu id name"} - bl_idname of menu to show.

The example of format can be found in the sverchok/index.yaml file (of current branch).

@Durman

1. IMHO these parameters
   
   should be in settings. In toolbar they just consume screen space.

Two questions:

1. Will the previous release (1.0) still be available for a while? I need to find time to understand and implement the needed changes to the Toplogic menu. Anyone willing to volunteer to do a PR on TopologicSverchok is much appreciated :) http://github.com/wassimj/TopologicSverchok
2. Does this release solve the issue of re-running a parent node if a new connection is made to a new child node? This is slowing execution big time as everytime I need the output for a second or third node, it re-runs potentially a very slow node rather than re-use the output already generated.

2. Also, can we have spacers in toolbar in the same places where we have them in menu? They are used to split long menu in smaller logical groups, it is useful in toolbar too.

3. Toolbar tooltips look like "Add SV node: description". IMHO 1) "Add SV node" phrase is not needed; 2) first line of tooltip should be the title of the node, because it is not visible anywhere in "icons only" mode.

should be in settings. In toolbar they just consume screen space.

I guess add-on settings should obtain properties which should be set once after add-on installation. It seemed to me that at least showing only icons property is useful to switch on/off depending on the filter output.

I will have a look at spaces and content of the tooltips.

@wassimj
It's not a release. This PR has description in the first post. Last release (1.1) will work fine with all Sverchok's extensions.

@portnov a74063a

I kindly need help making topologic compatible with sverchok 1.2. The current init file is at (https://github.com/wassimj/TopologicSverchok/blob/main/__init__.py). Would someone from the sverchok team be willing to suggest how to edit it with examples so it does not break the way it imports 3rd party libraries? Thank you.

@wassimj I will have a look.